Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications


Building a customized executable in Windows

This section contains instructions for building 4GL client or AppServer executables running in Windows to access custom C functions. The script is located in the oebuild/make directory under the root of your OpenEdge installation.

To build a Windows 4GL client executable:

  1. Log in as Administrator and run the Proenv utility (Start Programs OpenEdge Proenv) on a system where OpenEdge is installed. This sets the DLC variable.
  2. Change directory to the OpenEdge make directory. For example:
  3. proenv> cd %DLC%\oebuild\make 
    

  4. Set up the Microsoft Visual C++ environment by running vcvars32.bat. For example:
  5. proenv> "C:\Program Files\Microsoft Visual Studio 
            .NET\Vc7\bin\vcvars32.bat" 
    

  6. Make a backup copy of the original OEBuild link options script and the 4GL tie-in object used to access custom C functions, hlprodsp.o. There are three versions of the OEBuild link options script, depending on the 4GL client executable you plan to build:
    • build_prow32.link — 4GL GUI client executable.
    • build__prchar.link — 4GL character client (or WebSpeedŽ agent) executable.
    • build__proapsv.link — AppServer agent executable.
    • For example, to copy the original GUI 4GL client and 4GL tie-in object:

      proenv> copy build_prow32.link build_prow32.link.orig 
      proenv> copy ..\obj\hlprodsp.obj ..\obj\hlprodsp.obj.orig 
      

  7. Edit the C source file for the 4GL tie-in object in order to tie in your C functions to the 4GL as explained in the source file comments. This file is located at the following path:
  8. %DLC%/oebuild/hlc/hlprodsp.c 
    

  9. Compile the new tie-in object. For example:
  10. proenv> cl -c -Fo ..\obj\hlprodsp.obj ..\hlc\hlprodsp.c 
    

  11. Edit the link options script for your executable (build_prow32.link, build__prchar.link, or build__proapsv.link) to add customized objects and any necessary libraries to accommodate them on the link line. Save the file.
  12. Run the link command to create a customized 4GL client dynamic link library (DLL). For example, to create a customized GUI 4GL client DLL:
  13.  proenv> link @build_prow32.link 
    

  14. Back up the original 4GL client DLL. For example:
  15. proenv> copy %DLC%\bin\prow32.dll %DLC%\bin\prow32.dll.orig 
    

  16. Copy the customized 4GL client DLL into the installed bin directory. For example:
  17. proenv> copy %DLC%\oebuild\make\prow32.dll %DLC%\bin\prow32.dll 
    


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095